<meta charset="utf-8">
(#) Include the fragment-testing-manifest library using the debugImplementation configuration

!!! ERROR: Include the fragment-testing-manifest library using the debugImplementation configuration
   This is an error.

Id
:   `FragmentGradleConfiguration`
Summary
:   Include the fragment-testing-manifest library using the debugImplementation configuration
Severity
:   Error
Category
:   Correctness
Platform
:   Android
Vendor
:   Android Open Source Project
Identifier
:   androidx.fragment.testing.manifest
Feedback
:   https://issuetracker.google.com/issues/new?component=460964
Min
:   Lint 7.0
Compiled
:   Lint 8.0 and 8.1
Artifact
:   [androidx.fragment:fragment-testing-manifest](androidx_fragment_fragment-testing-manifest.md.html)
Since
:   1.6.0
Affects
:   Gradle build files
Editing
:   This check runs on the fly in the IDE editor
See
:   https://d.android.com/training/basics/fragments/testing#configure
Implementation
:   [Source Code](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:/fragment/fragment-testing-manifest-lint/src/main/java/androidx/fragment/testing/manifest/lint/GradleConfigurationDetector.kt)
Tests
:   [Source Code](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:/fragment/fragment-testing-manifest-lint/src/test/java/androidx/fragment/testing/manifest/lint/GradleConfigurationDetectorTest.kt)
Copyright Year
:   2019

The fragment-testing-manifest library defines an EmptyActivity
     used when using FragmentScenario. Howver, it only needs to be
present in testing                configurations therefore use this
dependency with the debugImplementation                configuration.

(##) Example

Here is an example of lint warnings produced by this check:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~text
build.gradle:2:Error: Replace with debugImplementation.
[FragmentGradleConfiguration]
    androidTestImplementation("androidx.fragment:fragment-testing-manifest:1.2.0-beta02")
    -------------------------------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Here is the source file referenced above:

`build.gradle`:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~groovy linenumbers
dependencies {
    androidTestImplementation("androidx.fragment:fragment-testing-manifest:1.2.0-beta02")
}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can also visit the
[source code](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:/fragment/fragment-testing-manifest-lint/src/test/java/androidx/fragment/testing/manifest/lint/GradleConfigurationDetectorTest.kt)
for the unit tests for this check to see additional scenarios.

The above example was automatically extracted from the first unit test
found for this lint check, `GradleConfigurationDetector.expectFail`.
To report a problem with this extracted sample, visit
https://issuetracker.google.com/issues/new?component=460964.

(##) Including

!!!
   This is not a built-in check. To include it, add the below dependency
   to your project.

```
// build.gradle.kts
implementation("androidx.fragment:fragment-testing-manifest:1.8.5")

// build.gradle
implementation 'androidx.fragment:fragment-testing-manifest:1.8.5'

// build.gradle.kts with version catalogs:
implementation(libs.fragment.testing.manifest)

# libs.versions.toml
[versions]
fragment-testing-manifest = "1.8.5"
[libraries]
# For clarity and text wrapping purposes the following declaration is
# shown split up across lines, but in TOML it needs to be on a single
# line (see https://github.com/toml-lang/toml/issues/516) so adjust
# when pasting into libs.versions.toml:
fragment-testing-manifest = {
    module = "androidx.fragment:fragment-testing-manifest",
    version.ref = "fragment-testing-manifest"
}
```

1.8.5 is the version this documentation was generated from;
there may be newer versions available.

[Additional details about androidx.fragment:fragment-testing-manifest](androidx_fragment_fragment-testing-manifest.md.html).
(##) Suppressing

You can suppress false positives using one of the following mechanisms:

* Using a suppression comment like this on the line above:

  ```kt
  //noinspection FragmentGradleConfiguration
  problematicStatement()
  ```

* Using a special `lint.xml` file in the source tree which turns off
  the check in that folder and any sub folder. A simple file might look
  like this:
  ```xml
  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;lint&gt;
      &lt;issue id="FragmentGradleConfiguration" severity="ignore" /&gt;
  &lt;/lint&gt;
  ```
  Instead of `ignore` you can also change the severity here, for
  example from `error` to `warning`. You can find additional
  documentation on how to filter issues by path, regular expression and
  so on
  [here](https://googlesamples.github.io/android-custom-lint-rules/usage/lintxml.md.html).

* In Gradle projects, using the DSL syntax to configure lint. For
  example, you can use something like
  ```gradle
  lintOptions {
      disable 'FragmentGradleConfiguration'
  }
  ```
  In Android projects this should be nested inside an `android { }`
  block.

* For manual invocations of `lint`, using the `--ignore` flag:
  ```
  $ lint --ignore FragmentGradleConfiguration ...`
  ```

* Last, but not least, using baselines, as discussed
  [here](https://googlesamples.github.io/android-custom-lint-rules/usage/baselines.md.html).

<!-- Markdeep: --><style class="fallback">body{visibility:hidden;white-space:pre;font-family:monospace}</style><script src="markdeep.min.js" charset="utf-8"></script><script src="https://morgan3d.github.io/markdeep/latest/markdeep.min.js" charset="utf-8"></script><script>window.alreadyProcessedMarkdeep||(document.body.style.visibility="visible")</script>